home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000456_news@columbia.edu_Sun Oct 1 10:24:01 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA24445
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sun, 1 Oct 1995 18:47:48 -0400
Received: by apakabar.cc.columbia.edu id AA11903
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sun, 1 Oct 1995 18:47:46 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!news.msfc.nasa.gov!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit Push Command
Message-Id: <1995Oct1.162401.62433@cc.usu.edu>
Date: 1 Oct 95 16:24:01 MDT
References: <Pine.OSF.3.91.950930132944.29387A-100000-100000-100000@io.UWinnipeg.ca>
Organization: Utah State University
Lines: 38
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <Pine.OSF.3.91.950930132944.29387A-100000-100000-100000@io.UWinnipeg.ca>, Jim Clark <clark@UWinnipeg.ca> writes:
> Hi
>
> Several months ago I asked about how to get Kermit to push back to the
> shell from which Kermit was called, rather than pushing to Dos. Shell was
> Wordperfect Office and solutions I received were specific to that shell.
> Is there any more general solution on the Kermit side; that is, can I
> control in anyway within Kermit or in calling Kermit whether Push starts a
> new command process or returns to the calling process? Seems to me that
> most people would want to return to calling shell rather than start a new
> process (e.g., to switch back and forth between Kermit and other
> programs). For example, that is what <Alt><F4> does in Procomm.
When Kermit "shells to DOS" it invokes the currently identified
command processor, named in DOS Environment line SHELL=. If the line does
not exist (as is the default on DOS machines) it uses the COMSPEC=
Environment line. The latter is normally COMSPEC=c:\dos\command.com.
Please see release doc file kermit.bwr, and search on occurences of
keyword SHELL.
Kermit has no way of knowing how it got invoked. Since DOS is not a
multitasking o/s, as we all know, Kermit's only choice is to invoke that
command processor in such a way that Kermit regains control when the
processor and its successors complete. The SHELL= line gives the user
control of which command process will be invoked as Kermit "shells" to it.
Joe D.
>
> Thanks
> Jim
>
> ****************************************************************************
> James M. Clark (204) 786-9313
> Department of Psychology (204) 786-1824 Fax
> University of Winnipeg clark@uwinnipeg.ca
> Winnipeg, Manitoba R3B 2E9 4L02A
> CANADA
> ****************************************************************************
>